Method and apparatus for specifying time-varying intelligent service-oriented model

ABSTRACT

A method and an apparatus for specifying a time-varying, intelligent service-oriented model are provided. A method implemented in a computer infrastructure having computer executable code embodied on a computer readable storage medium having programming instructions, includes defining information of a service which is to be provided to one or more users having access to a system storing the defined information. The method further includes defining policies associated with the defined information to allow and deny access to selected portions of the defined information, and exposing to a user of the one or more users the selected portions of the defined information based on the defined policies allowing access to the selected portions of the defined information.

TECHNICAL FIELD

The present invention generally relates to an information technology(IT) environment model, and more particularly, to a method and anapparatus for specifying a time-varying, intelligent service-orientedmodel.

BACKGROUND

The Common Information Model (CIM) is an information technology (IT)environment model that defines how managed elements are represented as aset of objects and the relationships between them. The CIM allowsconsistent management of these managed elements. More specifically,every object in the CIM has its structural behavior specified throughits attributes (e.g., types), operations on the attributes, andrelationships with other objects. For example, an object can include atype attribute of an address, a billing address, and/or a serviceaddress that is set by a user, and can be linked to another objectincluding a similar type attribute.

However, the CIM imposes a constraint that every object is static. Inother words, every object and its attributes and relationships areunchanged until updated by a user. Accordingly, in a system or serviceusing the CIM, a manifestation of one object (e.g., service address) mayrequire a manifestation of its attributes and relationships to anotherobject (e.g., address), even though some of the attributes andrelationships should not be exposed for security reasons. To preventthis unnecessary exposure, a system may require additional securitylayers that may filter the secure attributes and relationships and/ormay restrict access of a particular user to the secure attributes andrelationships. In addition, the static nature of objects in the CIMimposes the need to manifest more objects and relationships thannecessary, from also a system efficiency and resources standpoint. Forexample, when a system needs to retrieve an object that is four nodesapart from a billing address object and/or three nodes apart from aservice address object, all of the nodes between the needed object andthe billing address object and/or the service address object may need tobe manifested, which degrades system efficiency and takes up systemresources. This excessive manifestation may occur even though only therelevant object needs to be manifested.

SUMMARY

In a first aspect of the invention, a method implemented in a computerinfrastructure having computer executable code embodied on a computerreadable storage medium having programming instructions, includesdefining information of a service which is to be provided to one or moreusers having access to a system storing the defined information. Themethod further includes defining policies associated with the definedinformation to allow and deny access to selected portions of the definedinformation, and exposing to a user of the one or more users theselected portions of the defined information based on the definedpolicies allowing access to the selected portions of the definedinformation.

In another aspect of the invention, a system is implemented in hardwarewhich includes a computer infrastructure operable to create a businessobject of a service provided to one or more users, and define a contextcomponent of the business object for manifestation of the businessobject. The context component includes at least one time period when thebusiness object is manifested to the one or more users. The computerinfrastructure is further operable to manifest the business object whena current time is within the at least one time period.

In an additional aspect of the invention, a computer program productincludes a computer usable storage medium having readable program codeembodied in the storage medium. The computer program product includes atleast one component operable to define information of a service which isto be provided to one or more users having access to a system storingthe defined information. The at least one component is further operableto define policies associated with the defined information to allow anddeny access to selected portions of the defined information, and exposeto a user of the one or more users the selected portions of the definedinformation based on the defined policies allowing access to theselected portions of the defined information.

In a further aspect of the invention, a method of specifying atime-varying, intelligent, service-oriented model, includes providing acomputer infrastructure, which is operable to request a service port foraccessing information of a service provided to one or more users, andrequest access of the information based on the service port. Thecomputer infrastructure is further operable to access the informationwhen the information is manifested based on parameters defined by theone or more users.

In another aspect of the invention, a computer system for specifying atime-varying, intelligent, service-oriented model is provided. Thesystem includes a CPU, a computer readable memory and a computerreadable storage media. First program instructions receive a requestfrom a user to access information that is stored on a system. Secondprogram instructions determine whether at least a first user and asecond user are authorized to have access to the information based ondefined rules as to time of retrieval. Third program instructionsprovide the first user access to a first type of the information whenthe first user is requesting access within the defined time ofretrieval, while denying access to additional information stored on thesystem. Fourth program instructions provide the second user access to asecond type of the information when the second user is requesting accesswithin the defined time of retrieval, while denying access to remaininginformation stored on the system. The first, second, third, and fourthprogram instructions are stored on the computer readable storage mediafor execution by the CPU via the computer readable memory.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 shows an illustrative environment of a sever and/or a computingdevice for implementing the steps in accordance with aspects of theinvention;

FIGS. 2-4 shows additional illustrative environments for implementingthe steps in accordance with aspects of the invention; and

FIGS. 5-8 show exemplary flows for specifying a time-varying,intelligent service-oriented model in accordance with aspects of theinvention.

DETAILED DESCRIPTION

The present invention generally relates to an information technology(IT) environment model, and more particularly, to a method and anapparatus for specifying a time-varying, intelligent service-orientedmodel. In embodiments, the present invention allows a user, while usinga service via a consumer device, to request to create one or morebusiness objects. In embodiments, these business objects may include anyelement or information of the service, such as an address of the user.The user request is transferred from the consumer device to a ContextAware Business Object Modeler (CABOM), which creates the businessobjects. Each of the business objects may include attributes andrelationships. For example, when one of the business objects includes anaddress of the user, attributes may include a street number and a streetname, and relationships may include a link to at least one otherbusiness object, such as a billing address object and/or a serviceaddress object.

In accordance with further aspects of the invention, the presentinvention enables time-intelligent objects. More specifically, duringcreation of the business objects, a user can specify context (e.g.,policies) of the business objects. For example, the user may set objecttype information of one of the business objects, e.g., specify that abusiness object is to manifest as, for example, a billing address objectand/or a service address object. Further, the user may set timeinformation of the business object, e.g., specify that the businessobject manifest, or be exposed, to particular users within particulartime periods. In addition, the object type information and the timeinformation may specify that specific attributes of the business objectmanifest within particular time periods, e.g., attributes “a” and “b”manifest in a first time period, while attributes “c” and “d” manifestin a second time period. In other words, the CABOM may perform atime-varying manifestation of the business objects, attributes of thebusiness objects, and/or relationships of the business objects. That is,the CABOM allows the behavior of the business objects to be based on theuser-specified context.

Advantageously, the present invention provides a time-varying objectmodel, instead of a static object model. The time-varying object modelcan increase security as the manifestation of business objects is morelimited, e.g., at only certain times and/or while other business objectsare hidden or not exposed to users. Also, via user-specified context ofbusiness objects, manifestation of the business objects may be limitedto a more granular (e.g., attribute and/or relationship) level, insteadof requiring all attributes and/or relationships to be exposed eventhough only relevant attributes and/or relationships are needed. Thismay also increase system security, while increasing system efficiency bydecreasing the amount of business objects and attributes manifested.

System Environment

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM),an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

FIG. 1 shows an illustrative environment 10 for managing the processesin accordance with the invention. To this extent, the environment 10includes a server or other computing system 12 that can perform theprocesses described herein. In particular, the server 12 includes acomputing device 14. The computing device 14 can be resident on anetwork infrastructure or computing device of a third party serviceprovider (any of which is generally represented in FIG.

1).

The computing device 14 also includes a processor 20, memory 22A, an I/Ointerface 24, and a bus 26. The memory 22A can include local memoryemployed during actual execution of program code, bulk storage, andcache memories which provide temporary storage of at least some programcode in order to reduce the number of times code must be retrieved frombulk storage during execution. In addition, the computing deviceincludes random access memory (RAM), a read-only memory (ROM), and anoperating system (O/S).

The computing device 14 is in communication with the external I/Odevice/resource 28 and the storage system 22B. For example, the I/Odevice 28 can comprise any device that enables an individual to interactwith the computing device 14 (e.g., user interface) or any device thatenables the computing device 14 to communicate with one or more othercomputing devices using any type of communications link. The externalI/O device/resource 28 may be for example, a handheld device, PDA,handset, keyboard, etc.

In general, the processor 20 executes computer program code (e.g.,program control 44), which can be stored in the memory 22A and/orstorage system 22B. Moreover, in accordance with aspects of theinvention, the program control 44 controls a service application 105 anda Context Aware Business Object Modeler (CAB OM) 110, e.g., theprocesses described herein. The service application 105 and the CABOM110 can be implemented as one or more program code in the programcontrol 44 stored in memory 22A as separate or combined modules.Additionally, the service application 105 and the CABOM 110 may beimplemented as separate dedicated processors or a single or severalprocessors to provide the function of this tool. Moreover, it should beunderstood by those of ordinary skill in the art that the serviceapplication 105 and the CABOM 110 are used as general descriptive termsfor providing the features and/or functions of the present invention,and that the service application 105 and the CABOM 110 may comprise manydifferent components such as, for example, the components and/orinfrastructure described and shown with reference to FIGS. 2-4.

In embodiments, the service application 105 can include any applicationor process engine that provides a service to a user. For example, theservice application 105 may include a Reliability, Availability andServiceability (RAS) application, a WebSphere® Integration Developer(WID) application, a WebSphere® Process Server (WPS) application, aWebSphere® Application Server (WAS) application, etc. WebSphere is atrademark of International Business Machines Corporation registered inmany jurisdictions worldwide. The service application 105 may provide aservice to a user via, e.g., a graphical user interface (GUI) of aconsumer device 120, which can include, for example, a personal computer(PC), a laptop, a smartphone, etc.

While using the service via the consumer device 120, a user can requestto create one or more business objects 115. In embodiments, thesebusiness objects 115 may include any element or information needed forthe service to be provided and/or provided by the service, such as anaddress of the user. The user request is transferred from the consumerdevice 120 to the service application 105, and to the CABOM 110, whichcreates the business objects 115. Each of the business objects 115 mayinclude attributes and relationships. For example, when one of thebusiness objects 115 includes an address of the user, attributes mayinclude a street number, street name, and a postal code of the address,and relationships may include a link to at least one other businessobject, such as a billing address object and/or a service addressobject. While the discussion herein mentions address information as anexample of information included in business objects, any information maybe contemplated by the present invention, e.g., invoice information,service information, telephone number information, office managementinformation, etc.

In accordance with further aspects of the invention, the CABOM 110enables creation time intelligent objects, which run on related timesensitive machines (TSM). More specifically, during creation of thebusiness objects 115, a user can specify context of (e.g., policiesassociated with) the business objects 115. For example, when defining anaddress, the user may set object type information or context of one ofthe business objects 115, e.g., specify that a business object is tomanifest as a billing address object and/or a service address object.The user may also set user information of one of the business objects115, e.g., specify that one or more certain users are able to bemanifested (e.g., to have access to) the business objects 115. Further,the user may set time information or context of the billing addressobject and/or the service address object, e.g., specify that the billingaddress object and/or the service address object manifest withinparticular time periods. In addition, the time information may specifythat specific attributes of the billing address object and/or theservice address object manifest within particular time periods, e.g.,attributes “a” and “b” manifest in a first time period, while attributes“c” and “d” manifest in a second time period. In embodiments, the timeinformation may specify that specific relationships of the billingaddress object and/or the service address object manifest withinparticular time periods. In other words, the CABOM 110 may perform atime-varying manifestation of the business objects 115, attributes ofthe business objects 115, and relationships of the business objects 115.That is, the CABOM 110 allows the behavior of the business objects 115to be based on the user-specified context (e.g., policies). Inembodiments, the business objects 115 and the context of the businessobjects 115 may be stored in the memory 22A and/or the storage system22B.

Advantageously, the present invention provides a time-varying objectmodel, instead of a static object model, to affect service-orientedarchitecture (SOA) behavior. The time-varying object model can increasesecurity as the behavior is controlled by time, not through uppersecurity layers. For example, a certain business object may bemanifested or exposed within particular time periods, instead of at eachparticular object request, while other business objects may remainhidden from users. Limited manifestation of business objects may lead toincreased security of business objects. Also, via user-specified contextof business objects, manifestation of the business objects may belimited at a more granular (e.g., attribute, relationship, user) level,instead of requiring all attributes and/or relationships to be exposedeven though only relevant attributes and/or relationships are needed.This may decrease the amount of business objects and attributesmanifested and thus, increase system efficiency.

By way of example, a user x may request the service application 105 tocreate an address business object including attributes of an address,such as a street number and/or a street name. The user x may alsorequest the address business object to have a defined context, e.g.,time information indicating that the address business object should bemanifested or exposed to users within a particular time period (between8:00 PM and 10:00 PM). The service application 105 forwards the userrequest to the CABOM 110, which creates the address business object anddefines the context of the address business object. When the CABOM 110determines that a current time is within the particular time period, theCABOM 110 manifests the address business object to the users, e.g., tobe requested for and retrieved by a user y. The CABOM 110 manifests theaddress business object to the users (e.g., the user y) for only theparticular time period. Accordingly, the context allows the addressbusiness object to be retrieved by only certain users (e.g., the user y)at certain times, and to be hidden from such users at other times. Inother words, the users get to see (request and retrieve) businessobjects that they need to see, and that they have permission to see.

While executing the computer program code, the processor 20 can readand/or write data to/from memory 22A, storage system 22B, and/or I/Ointerface 24. The program code executes the processes of the invention.The bus 26 provides a communications link between each of the componentsin the computing device 14.

The computing device 14 can comprise any general purpose computingarticle of manufacture capable of executing computer program codeinstalled thereon (e.g., a personal computer, server, etc.). However, itis understood that the computing device 14 is only representative ofvarious possible equivalent-computing devices that may perform theprocesses described herein. To this extent, in embodiments, thefunctionality provided by the computing device 14 can be implemented bya computing article of manufacture that includes any combination ofgeneral and/or specific purpose hardware and/or computer program code.In each embodiment, the program code and hardware can be created usingstandard programming and engineering techniques, respectively.

Similarly, the computing infrastructure 12 is only illustrative ofvarious types of computer infrastructures for implementing theinvention. For example, in embodiments, the server 12 comprises two ormore computing devices (e.g., a server cluster) that communicate overany type of communications link, such as a network, a shared memory, orthe like, to perform the process described herein. Further, whileperforming the processes described herein, one or more computing deviceson the server 12 can communicate with one or more other computingdevices external to the server 12 using any type of communications link.The communications link can comprise any combination of wired and/orwireless links; any combination of one or more types of networks (e.g.,the Internet, a wide area network, a local area network, a virtualprivate network, etc.); and/or utilize any combination of transmissiontechniques and protocols.

FIG. 2 shows another illustrative environment 200 for implementing thesteps in accordance with aspects of the invention. In embodiments, theenvironment 200 can include the service application 105, the CABOM 110,an address object 205, a service address object 210, a billing addressobject 215, a context component 220, and a business object component225. The service application 105 and the CABOM 110 may include theservice application 105 and the CABOM 110 in FIG. 1.

In embodiments, the service application 105 can include any applicationor process engine that provides a service to a user. For example, theservice application 105 may include a Reliability, Availability andServiceability (RAS) application, a WebSphere® Integration Developer(WID) application, a WebSphere® Process Server (WPS) application, aWebSphere® Application Server (WAS) application, etc. WebSphere is atrademark of International Business Machines Corporation registered inmany jurisdictions worldwide. The service application 105 may provide aservice to a user via, e.g., a graphical user interface (GUI) of aconsumer device, e.g., the consumer device 120 in FIG. 1.

In accordance with further aspects of the invention, a user can requestto create one or more business objects, e.g., the address object 205. Inembodiments, these business objects may include any element orinformation needed for the service to be provided and/or provided by theservice, such as an address of the user. The user request is transferredfrom the consumer device to the service application 105, and to theCABOM 110, which creates the business objects. While the discussionherein mentions business objects including exemplary addressinformation, the present invention contemplates business objects toinclude any type of information may, e.g., invoice information, serviceinformation, telephone number information, office managementinformation, etc. The created business objects may be stored in memory(e.g., the memory 22A in FIG. 2) and/or a storage system (e.g., thestorage system 22B in FIG. 2).

In embodiments, the CABOM 110 can create the address object 205, whichcan include attributes and relationships of an address of the user. Forexample, the attributes of the address object 205 may include an addressidentifier (ID), a street name, a street number, a locality, a postalcode, a country, a state, text, etc. The relationships of the addressobject 205 may include a link to the service address object 210 and thebilling address object 215, where the address object 205 may inheritattributes of the service address object 210 and/or the billing addressobject 215.

In accordance with further aspects of the invention, the CABOM 110 mayalso create the service address object 210 and the billing addressobject 215, which may include attributes and relationships of a serviceaddress or a billing address of the user. The attributes of the serviceaddress object 210 and the billing address object 215 may include thosesimilar to the attributes of the address object 205, e.g., the addressID, country, state, etc. The attributes of the service address object210 and the billing address object 215 may also include differentattributes, e.g., the billing address object 215 includes a post office(P.O.) box number, while the service address object 210 does not includea P.O. box number. The relationships of the service address object 210and the billing address object 215 may include links to the addressobject 205, where the address object 205 may inherit the attributes ofthe service address object 210 and/or the billing address object 215.

In embodiments, based on the user request to create business objects,the CABOM 110 can define the context component 220 of (e.g., policiesassociated with) the business objects, e.g., the address object 205, theservice address object 210, and/or the billing address object 215. Thecontext component 220 allows the user to specify how the businessobjects should behave, namely, what attributes of the business objectsare exposed and what operations can be performed on the business objectswithin particular time periods for possibly a specified set of users.For example, the context component 220 may include a service operation,object type information, time information, etc., to develop the runtimebehavior of the business objects. The service operation may include anoperator or function identifier (ID) that indicates an operation (e.g.,read, manifest, or write a business object, and/or calculate anattribute of a business object) the CABOM 110 is to perform. The objecttype information may include an object type (e.g., service addressand/or billing address, logical resource management and/or physicalresource management), attributes, and/or relationships that an operationshould be performed to or from. The time information may include, forexample, a particular time period (e.g., between 6:00 PM to 8:00 PM) anoperation should be performed. Each of the service operation, the objecttype information, and the time information may be defined when theaddress object 205, the service address 210, and/or the billing addressobject 215 are created. In another example, the context component 220may include user information that indicates one or more users that mayperform an operation associated with (e.g., access) the businessobjects.

For example, the context component 220 may include a service operationthat indicates a manifest operation of the CABOM 110. The contextcomponent 220 may further include object type information of a serviceaddress, and time information of a particular time period between 6:00PM to 8:00 PM. Accordingly, the context component 220 instructs theCABOM 110 to manifest the service address object 210 (and possibly theaddress object 205) between 6:00 PM to 8:00 PM. In another example, thecontext component 220 may include a service operation that indicates themanifest operation of the CABOM 110. The context component 220 mayfurther include an object type information of a billing address, andtime information of a particular time period between 8:00 PM to 10:00PM. Accordingly, the context component 220 instructs the CABOM 110 tomanifest the billing address object 215 (and possibly the address object205) between 8:00 PM to 10:00 PM. The defined context component 220 maybe stored in memory (e.g., the memory 22A in FIG. 2) and/or a storagesystem (e.g., the storage system 22B in FIG.

2).

In accordance with further aspects of the invention, based on theservice address object 210 (and possibly the address object 205) and thecontext component 220, the CABOM 110 determines whether a current timeis between the particular time period of 6:00 PM to 8:00 PM, forexample. When the current time is between the particular time period,the CABOM 110 manifests the service address object 210 (and possibly theaddress object 205) based on the context component 220. Otherwise, theservice address object 210 is hidden from or not exposed to users. Basedon the billing address object 215 (and possibly the address object 205)and the context component 220, the CABOM 110 determines whether thecurrent time is between the particular time period of 8:00 PM to 10:00PM, for example. When the current time is between this time period, theCABOM 110 manifests (e.g., shows) the billing address object 215 (andpossibly the address object 205) based on the context component 220.Otherwise, the billing address object 215 is hidden from or not exposedto users.

In embodiments, the address object 205, the service address object 210,and/or the billing address object 215 can be manifested into a businessobject component 225, which inherits the attributes and therelationships of the objects 205, 210, and/or 215. When serviceapplication 105 requests a business object from the CABOM 110, the CABOM110 may return the business object component 225 to the serviceapplication 105, which may return or expose the business objectcomponent 225 to the user of the consumer device. Advantageously, therun time behavior of the address object 205, the service address object210, and the billing address object 215 may be driven by the contextcomponent 220, imposing security and reaping system efficiency benefits.

FIG. 3 shows another illustrative environment 300 for implementing thesteps in accordance with aspects of the invention. In embodiments, theenvironment 300 can include the service application 105, the CABOM 110,an address object 305, a service address object 310, a billing addressobject 315, a context component 320, and a business object component325. The service application 105 and the CABOM 110 may include theservice application 105 and the CABOM 110 in FIG. 1. While thediscussion herein mentions business objects including addressinformation (e.g., the address object 305) as an example, the businessobjects of the present invention may include any type of information,e.g., invoice information, service information, telephone numberinformation, office management information, etc.

In an exemplary operation of the present invention, the serviceapplication 105 sends to the CABOM 110 a user request to create theaddress object 305, the service address object 310, and/or the billingaddress object 315, and to define the context component 320 of theaddress object 305. Based on the user request, the CABOM 110 creates theaddress object 305, which includes attributes such as at least oneaddress identifier (ID) and at least one address of the user. Inembodiments, the address ID may include an ID of a service address (SA)type and/or a billing address (BA) type. The CABOM 110 may also createthe service address object 310 and the billing address object 315, whichinclude attributes such as at least one service address and at least onebilling address, respectively, of the user. The CABOM 110 may create theaddress object 305, the service address object 310, and the billingaddress object 315 to include relationships with each other, e.g.,indications that the address object 310 inherits the attributes of theservice address object 310 and/or the billing address object 315. As itcreates the address object 305, the service address object 310, and thebilling address object 315, the CABOM 110 may prompt the user to linkthese objects 305, 310, 315 to the context component 320.

In embodiments, based on the user request, the CABOM 110 defines thecontext component 320. For example, the context component 320 caninclude a service operation of “Retrieve Address”, which instructs theCABOM 110 to manifest or expose an address of the user for retrieval bythe user via a consumer device (e.g., the consumer device 120 in FIG.1). The context component 320 may further include object typeinformation of the SA type, and time information of a particular timeperiod between 8:00 PM to 10:00 PM. In addition, the context component320 may include object type information of the BA type, and timeinformation of a particular time period between 10:00 PM to 12:00 AM.Accordingly, the context component 320 instructs the CABOM 110 tomanifest the service address of the user from 8:00 PM-10:00 PM, and tomanifest the billing address of the user from 10:00 PM-12:00 AM.

In accordance with further aspects of the present invention, based onthe time information of the context component 320, the CABOM 110determines whether a current time is within the time period between 8:00PM to 10:00 PM. If the current time is within this time period, theCABOM 110 manifests the service address of the user in the serviceaddress object 310. In embodiments, the CABOM 110 can manifest theservice address by transferring the service address from the serviceaddress object 310 through the address object 305 and to the businessobject component 325. When the user requests the service address, theCABOM 110 may then return the business object component 325 through theservice application 105 to the consumer device of the user.Alternatively or additionally, the CABOM 110 may manifest (e.g., pull)the service address object 310 and/or the business object component 325such that the consumer device may directly access (e.g., request) theservice address object 310 and/or business object component 325 forretrieval of the service address. When the current time is no longerwithin the time period between 8:00 PM to 10:00 PM, the CABOM 110 stopsmanifesting the service address object 310 and/or the business objectcomponent 325.

Advantageously, external consumers will not be made aware of or be ableto access the service address after the time period as the manifestationof the service address will cease after the time period, ensuring strictsecurity of the service address. In addition, during the time period,the CAB OM 110 does not have to manifest the billing address and otherattributes of the address object 305, thus reducing resourceconsumption. Instead, the context component 305 defines a direct accessto the relevant attribute in the service address object 310. Forexample, the context component 305 may include object type informationof the SA type and the relevant attribute in the service address object310.

In embodiments, based on the time information of the context component320, the CABOM 110 determines whether a current time is within the timeperiod between 10:00 PM to 12:00 AM. If the current time is within thistime period, the CABOM 110 manifests the billing address of the user inthe billing address object 315. In embodiments, the CABOM 110 canmanifest the billing address by transferring the billing address fromthe billing address object 315 through the address object 305 and to thebusiness object component 325. When the user requests the billingaddress, the CABOM 110 may then return the business object component 325through the service application 105 to the consumer device of the user.Alternatively or additionally, the CABOM 110 may manifest (e.g., pull)the billing address object 315 and/or the business object component 325such that the consumer device may directly access (e.g., request) thebilling address object 315 and/or business object component 325 forretrieval of the billing address. When the current time is no longerwithin the time period between 10:00 PM to 12:00 AM, the CABOM 110 stopsmanifesting the billing address object 315 and/or the business objectcomponent 325.

Advantageously, external consumers will not be made aware of or be ableto access the billing address after the time period as the manifestationof the billing address will cease after the time period, ensuring strictsecurity of the billing address. Further, during the time period, theCABOM 110 does not have to manifest the service address and otherattributes of the address object 305, thus reducing resourceconsumption. Instead, the context component 305 defines a direct accessto the relevant attribute in the billing address object 315.

FIG. 4 shows another illustrative environment 400 for implementing thesteps in accordance with aspects of the invention. In embodiments, theenvironment 400 can include the service application 105, the CABOM 110,the service address object 310, the billing address object 315, thecontext component 320, and the business object component 325. Theservice application 105 and the CABOM 110 may include the serviceapplication 105 and the CABOM 110 in FIG. 1. The service address object310, the billing address object 315, the context component 320, and thebusiness object component 325 may include the service address object310, the billing address object 315, the context component 320, and thebusiness object component 325 in FIG. 3. The environment 400 furtherincludes an address object 405 and a sub-address object 410.

In an exemplary operation of the present invention, the serviceapplication 105 sends to the CABOM 110 a user request to create theaddress object 405, the service address object 310, the billing addressobject 315, and/or the sub-address object 410, and to define the contextcomponent 320 of the address object 405. Based on the user request, theCABOM 110 creates the address object 405, which includes attributes suchas at least one address identifier (ID), a parent address ID, a propertyname, a street name, a “from” street number suffix, a “from” streetnumber, a “to” street number, a street type suffix, a street type, alocality name, a locality ID, a state or province, a postal code, acountry, a latitude, a longitude, address additional information, anaddress status, address-specific information, and a postal (P.O.) boxnumber. Other information can be included. The address object 405 mayfurther include relationships that relate the address object 405 toother business objects. For example, the address object 405 may includean address reference that may refer to the service address object 310and/or the billing address object 315, and a sub-address reference thatmay refer to the sub-address object 410. In embodiments, each of theattributes and relationships of the address object 405 may include aservice address ID (SA) and/or a billing address ID (BA) that indicatewhether an attribute or relationship is an attribute or relationship ofthe service address object 305 and/or the billing address object 315,respectively.

In accordance with further aspects of the invention, the CABOM 110 mayalso create the sub-address object 410, which include attributes such asa parent address ID, a sub-address ID, a building name, a building type,a building number, a level number, a level type, a private street name,a private street type, a unit number, a unit number suffix, a unit type,a sub-address status, a private street suffix, and sub-addressadditional information. The sub-address object 410 may further includerelationships that relate the sub-address object 410 to other businessobjects. For example, the sub-address object 410 may include asub-address reference that refers to the address object 405, the serviceaddress object 310, and/or the billing address object 315.

In embodiments, the CABOM 110 may create the address object 405, thesub-address object 410, and the service address object 310, and thebilling address object 315 to include relationships with each other,e.g., indications that the address object 405 inherits the attributes ofthe sub-address object 410, the service address object 310, and/or thebilling address object 315. As it creates the address object 405, thesub-address object 410, the service address object 310, and the billingaddress object 315, the CABOM 110 may prompt the user to link theseobjects 405, 410, 310, 315 to the context component 320.

In embodiments, based on the user request, the CABOM 110 defines thecontext component 320. For example, the context component 320 caninclude a service operation of “Retrieve Address”, which instructs theCABOM 110 to manifest or expose an address of the user for retrieval bythe user via a consumer device (e.g., the consumer device 120 in FIG.1). The context component 320 may further include object typeinformation of a SA type, and time information of a particular timeperiod between 8:00 PM to 10:00 PM. In addition, the context component320 may include object type information of a BA type, and timeinformation of a particular time period between 10:00 PM to 12:00 AM.Accordingly, the context component 320 instructs the CABOM 110 tomanifest the service address of the user from 8:00 PM-10:00 PM, and tomanifest the billing address of the user from 10:00 PM-12:00 AM.

In accordance with further aspects of the invention, the contextcomponent 320 may also instruct the CABOM 110 to manifest the attributesand relationships of the address object 405 related to the serviceaddress of the user from 8:00 PM-10:00 PM, and to manifest theattributes of the address object 405 related to the billing address ofthe user from 10:00 PM-12:00 AM. For example, when a current time isbetween 8:00 PM-10:00 PM, the CABOM 110 may manifest the service addressobject 310 and the related attributes of the address object 405, such asthe property name, the street name and the “from” street number suffix.In another example, when the current time is between 10:00 PM-12:00 AM,the CABOM 110 may manifest the billing address object 315 and therelated attributes of the address object 405, such as the P.O. boxnumber. Depending on the object type information in the contextcomponent 320, the CABOM 110 may further manifest the attributes andrelationships of the sub-address object 410 during particular timeperiods.

FIGS. 5-8 show exemplary flows for performing aspects of the presentinvention. The steps of FIG. 5-8 may be implemented in the environmentof FIGS. 1-4, for example.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. The software and/or computer programproduct can be implemented in the environment of FIGS. 1-4. For thepurposes of this description, a computer-usable or computer readablemedium can be any apparatus that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device. The medium can be anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system (or apparatus or device) or a propagation medium.Examples of a computer-readable storage medium include a semiconductoror solid state memory, magnetic tape, a removable computer diskette, arandom access memory (RAM), a read-only memory (ROM), a rigid magneticdisk and an optical disk. Current examples of optical disks includecompact disk—read only memory (CD-ROM), compact disc—read/write (CD-R/W)and DVD.

FIG. 5 depicts an exemplary flow for a process 500 of specifying atime-varying, intelligent service-oriented model in accordance withaspects of the invention. The process 500 involves five players: theservice application, the CABOM 110, and the consumer device 120 in FIG.1, and the service address object 310 and the business address objet 315in FIG. 3. At step S505, the process starts, and the consumer device 120requests to retrieve a service port of the service address object 310from the service application 105. At step S510, the service application105 determines the service port of the service address object 310. Atstep S515, the service application 105 returns the service port of theservice address object 310 to the consumer device 120.

At step S520, based on a context component (e.g., the context component320 in FIG. 3) of the service address object 310, the CAB OM 110determines whether a current time is within a particular time period(e.g., 8:00-10:00 PM), which is set as time information in the contextcomponent. If the current time is within the particular time period,then at step S525, the CABOM 110 instructs the service address object310 to manifest or expose its attributes and relationships to at leastthe consumer device 120 based on the context component. At step S530,the service address object 310 manifests its attributes andrelationships to at least the consumer device 120 based on the contextcomponent.

At step S535, the consumer device 120 requests at least one attribute(e.g., a service address) of the service address object 310. At stepS540, the service address object 310 processes the request from theconsumer device 120, and at step S545, the service address object 310sends the request attribute to the consumer device 120. At step S550,the service address object 310 determines that the current time is nolonger within the particular time period, stops manifesting theattributes and relationships, and informs the CABOM 110 that suchattributes and relationships are no longer manifested.

At step S555, based on the context component (e.g., the contextcomponent 320 in FIG. 3) of the billing address object 315, the CABOM110 determines whether the current time is within another particulartime period (e.g., 10:00 PM-12:00 AM), which is set as the timeinformation in the context component. If the current time is within theparticular time period, then at step S560, the CABOM 110 instructs thebilling address object 315 to manifest or expose its attributes andrelationships to at least the consumer device 120 based on the contextcomponent. At step S565, the billing address object 315 manifest itsattributes and relationships to at least the consumer device 120 basedon the context component. At step S570, the billing address object 315determines that the current time is no longer within the particular timeperiod, stops manifesting the attributes and relationships, and informsthe CABOM 110 that such attributes and relationships are no longermanifested. At step S570, the process ends.

FIG. 6 depicts another exemplary flow for a process 600 of specifying atime-varying, intelligent service-oriented model in accordance withaspects of the invention. In embodiments, the process 600 can beperformed by a Context Aware Business Object Modeler (CABOM), forexample, the CABOM 110 in FIGS. 1-4. At step 605, the process starts.

At step 610, the CABOM defines information of a service and/or a serviceprovider. For example, the CABOM can create a business object (e.g., theaddress object 205, the service address object 210, and/or the billingaddress object 215 in FIG. 2) of the information, including attributes(e.g., an address of a user and/or other information) and relationships.At step 615, the CABOM defines parameters for access (e.g., read and/orwrite) of the defined information by one or more users. For example, theCABOM can define a context component (e.g., the context component 220 inFIG. 2) of the business object, including a service operation, objecttype information (e.g., a service address object type and/or a billingaddress object type that is manifested or exposed), and time information(e.g., a particular time period when the business object is manifested).

At step 620, the CABOM allows access of the information based on thedefined parameters. For example, the CABOM can determine whether acurrent time is within a particular time period (e.g., 8:00 PM-10:00 PM)defined in the time information of the context component. If the currenttime is within the particular time period, the CABOM manifests thebusiness object to at least a service application and/or a consumerdevice of a user (e.g., the service application 105 and the consumerdevice 120 in FIG. 1) such that the user may access the business object.In embodiments, the CABOM may manifest the business object bytransferring the at least one attribute from the business object to abusiness object component (e.g., the business object component 325 inFIG. 3). When a user requests the attribute, the CABOM may then returnthe business object component through the service application to theconsumer device. Alternatively or additionally, the CABOM may manifest(e.g., pull) the business object and/or the business object componentsuch that the consumer device may directly access (e.g., request) thebusiness object and/or business object component. At step 625, theprocess ends.

FIG. 7 depicts another exemplary flow for a process 700 of specifying atime-varying, intelligent service-oriented model in accordance withaspects of the invention. In embodiments, the process 700 can beperformed by a Context Aware Business Object Modeler (CABOM), forexample, the CABOM 110 in FIGS. 1-4. At step 705, the process starts.

At step 710, the CABOM creates a business object (e.g., the addressobject 205, the service address object 210, and/or the billing addressobject 215 in FIG. 2) including attributes and relationships. At step715, the CABOM defines a context component (e.g., the context component220 in FIG. 2) of the business object, including a service operation,object type information (e.g., a service address object type and/or abilling address object type), and time information (e.g., a particulartime period when the business object is manifested or exposed). At step720, the CABOM determines whether a current time is within a particulartime period (e.g., 8:00 PM-10:00 PM) defined in the time information ofthe context component. If the current time is within the particular timeperiod, the process continues at step 725. Otherwise, the processreturns to step 720.

At step 725, the CABOM manifests the business object to at least aservice application and/or a consumer device of a user (e.g., theservice application 105 and the consumer device 120 in FIG. 1). Inembodiments, the CABOM can manifest the business object by transferringthe at least one attribute from the business object to a business objectcomponent (e.g., the business object component 325). When the userrequests the attribute, the CABOM may then return the business objectcomponent through the service application to the consumer device.Alternatively or additionally, the CABOM may manifest (e.g., pull) thebusiness object and/or the business object component such that theconsumer device may directly access (e.g., request) the business objectand/or business object component for retrieval of the attribute.

At step 730, the CABOM determines whether the user request has beenreceived. If the user request has been received, the process continuesat step 735. Otherwise, the process continues at step 740. At step 735,the CABOM sends the business object to the service application, whichmay subsequently send the business object to the consumer device. Atstep 740, the CABOM again determines whether the current time is withinthe particular time period defined in the time information of thecontext component. If the current time is still within the particulartime period, the process returns to step 730. Otherwise, the processcontinues at step 745. At step 745, the CABOM stops manifesting thebusiness object to at least the service application and/or the consumerdevice. At step 750, the process ends.

FIG. 8 depicts another exemplary flow for a process 800 of accessing atime-varying, intelligent service-oriented model in accordance withaspects of the invention. In embodiments, the process 800 can beperformed by a consumer device, for example, the consumer device 120 inFIGS. 1 and 5. At step 805, the process starts.

At step 810, the consumer device requests a service port for accessinginformation of a service, from a service application (e.g., the serviceapplication 105 in FIG. 1), for example. In embodiments, the informationcan include a business object (e.g., the address object 205, the serviceaddress object 210, and/or the billing address object 215 in FIG. 2)with attributes (e.g., an address of a user and/or other information)and relationships. At step 815, the consumer device determines whetherit receives the service port. If the consumer device receives theservice port, the process continues at step 820. Otherwise (e.g., theconsumer device does not receive the service port within a predeterminedperiod of time and/or the consumer device receives a message from theservice application that denies access to the information), the processends at step 835.

At step 820, the consumer device requests access (e.g., read and/orwrite) of the information from the services application and/or fromdirectly the business object. At step 825, the consumer devicedetermines whether it receives a message from, e.g., the serviceapplication, that denies access to the information for one of variousreasons, such as the requested information is not manifested or exposedat a current time and/or a particular type of the requested informationis not manifested. In embodiments, the requested information may not bemanifested due to parameters of information access previously defined bya user (e.g., the context component 220 in FIG. 2). If the consumerdevice does not receive the access denial message, the process continuesat step 830. Otherwise, the process ends at step 835. At step 830, theconsumer device accesses the information directly and/or through theservice application. At step 835, the process ends.

In embodiments, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. These customers may be, for example, anybusiness that uses technology. In return, the service provider canreceive payment from the customer(s) under a subscription and/or feeagreement and/or the service provider can receive payment from the saleof advertising content to one or more third parties.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims, if applicable, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of the present invention has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the invention in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The embodiment was chosen and described in order to best explain theprincipals of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated. Accordingly, while the invention has beendescribed in terms of embodiments, those of skill in the art willrecognize that the invention can be practiced with modifications and inthe spirit and scope of the appended claims.

What is claimed is:
 1. A method comprising: defining information of aservice which is to be provided to one or more users having access to asystem storing the defined information; and permitting, by a processor,a user of the one or more users with access to the selected portions ofthe defined information based on defined policies identifying that theuser of the one or more users is permitted to access the selectedportions of the defined information, wherein: the defined information iscontained in at least one business object; and the defined policies areassociated with the defined information and comprise time information ofthe at least one business object, the time information specifying one ormore time periods when the user is permitted to access to the selectedportions of the defined information.
 2. The method of claim 1, whereinthe defined policies comprise at least one service operation which theuser is allowed to perform on the defined information.
 3. The method ofclaim 1, wherein the defined policies comprise at least one type ofinformation of the defined information which the user is permitted toaccess, while denying access to another type of information of thedefined information.
 4. The method of claim 1, wherein the definedinformation and the defined policies are defined by at least one of theone or more users and a service provider.
 5. The method of claim 1,wherein the at least one business object comprises at least one of: oneor more attributes of the one or more users; and one or morerelationships between the at least one business object and otherbusiness objects.
 6. The method of claim 5, wherein the defined policiescomprise at least one attribute of the one or more attributes that theuser is permitted to access.
 7. The method of claim 5, wherein thedefined policies comprise at least one relationship of the one or morerelationships that the user is permitted to access.
 8. The method ofclaim 1, wherein: the defined policies associated with the businessobject comprise type information, the type information including a firsttype and a second type; the selected portions of the defined informationinclude a first attribute of the first type and a second attribute ofthe second type; the selected portions of the defined informationinclude a first relationship to the first attribute and a secondrelationship to the second attribute; the time information specifiesthat the user is permitted to access to the first attribute during afirst time period of the one or more time periods; and the timeinformation specifies that the user is permitted access to the secondattribute during a second time period of the one or more time periods.9. The method of claim 1, wherein the exposing the selected portions ofthe defined information comprises: manifesting, based on the timeinformation and the type information, the first attribute and the firstrelationship to a device of the user when a current time is within thefirst time period; stopping manifesting the first attribute and thefirst relationship when the current time is no longer within the firsttime period; manifesting, based on the time information and the typeinformation, the second attribute and the second relationship to thedevice of the user when the current time is within the second timeperiod; and stopping manifesting the second attribute and secondrelationship when the current time is no longer within the second timeperiod.
 10. The method of claim 9, wherein the type informationspecifies that the at least one business object is to manifest as one ofa billing address object and a service address object.
 11. The method ofclaim 9 further comprising sending the business object to a requestingconsumer device based on manifesting the business object.
 12. The methodof claim 1, further comprising: preventing the user from accessing theselected portions of the defined information outside the one or moretime periods when the user is permitted to access the selected portionsof the defined information.
 13. The method of claim 1, furthercomprising defining a context component of the business object, whereindefining information of the service includes defining the contextcomponent.